EVPN Route Targets

EVPN Route Targets
A new keyword is added to the existing route-target configuration to specify the route targets to be used when
doing EVPN-VXLAN related processing. The base (existing) route target configuration does not affect
EVPN-VXLAN related processing. You can have the same RT values for both base and vxlan routes
MAC/IP Advertisement Route and IP Prefix Route is supported. The l2vpn evpn address-family can be
configured and neighbors can exchange EVPN NLRI. The l2vpn-evpn-prefix-advertisement issupported fully
and for the non-MAC portions only the NLRI is supported. IP Prefix route type is added to carry IP prefixes.
The IP Prefix NLRI can carry IPv4 Prefix or IPv6 Prefix. The NLRI length determines whether it has IPv4
Prefix or IPv6 Prefix.
NLRI Format:
[Type][Len][RD][ESI][ETag][IP Addr Mask][IP Addr][GW IP Addr][Label]

Key:
[Type][ETag][IP Addr Len][IP Addr]

When BGP attribute, encapsulation type EXTCOMM value of 0x8 ( VxLAN ) is present, then Label carries
VNI (VXLAN ID).
EVPN RT5 and RT2 that contain a RT matching an import “stitching RT” specified in a vrf configuration is
accepted by the router and imported into the corresponding BGP L3VPN vrf. The resulting L3VPN prefix
retains the same route target. L3VPN routes that are imported into EVPN via “advertise l2vpn evpn” contains
route targets specified by that vrf’s export “stitching RT”. Any original route targets is removed